Computer Science

Extreme Programming Explained: Embrace Change (The XP Series)

Extreme Programming Explained: Embrace Change (The XP Series)

  • Downloads：3267
  • Type：Epub+TxT+PDF+Mobi
  • Create Date：2021-09-23 09:55:08
  • Update Date：2025-09-07
  • Status：finish
  • Author：Kent Beck
  • ISBN：0321278658
  • Environment：PC/Android/iPhone/iPad/Kindle
  • Download

Summary

"In this second edition of Extreme Programming Explained， Kent Beck organizes and presents five years' worth of experiences， growth， and change revolving around XP。 If you are seriously interested in understanding how you and your team can start down the path of improvement with XP， you must read this book。"

-- Francesco Cirillo， Chief Executive Officer， XPLabs S。R。L。 "The first edition of this book told us what XP was--it changed the way many of us think about software development。 This second edition takes it farther and gives us a lot more of the 'why' of XP， the motivations and the principles behind the practices。 This is great stuff。 Armed with the 'what' and the 'why， ' we can now all set out to confidently work on the 'how' how to run our projects better， and how to get agile techniques adopted in our organizations。"

-- Dave Thomas， The Pragmatic Programmers LLC "This book is dynamite！ It was revolutionary when it first appeared a few years ago， and this new edition is equally profound。 For those who insist on cookbook checklists， there's an excellent chapter on 'primary practices， ' but I urge you to begin by truly contemplating the meaning of the opening sentence in the first chapter of Kent Beck's book: 'XP is about social change。' You should do whatever it takes to ensure that every IT professional and every IT manager--all the way up to the CIO--has a copy of Extreme Programming Explained on his or her desk。"

-- Ed Yourdon， author and consultant "XP is a powerful set of concepts for simplifying the process of software design， development， and testing。 It is about minimalism and incrementalism， which are especially useful principles when tackling complex problems that require a balance of creativity and discipline。"

-- Michael A。 Cusumano， Professor， MIT Sloan School of Management， and author of The Business of Software " Extreme Programming Explained is the work of a talented and passionate craftsman。 Kent Beck has brought together a compelling collection of ideas about programming and management that deserves your full attention。 My only beef is that our profession has gotten to a point where such common-sense ideas are labeled 'extreme。'。。。"

-- Lou Mazzucchelli， Fellow， Cutter Business Technology Council "If your organization is ready for a change in the way it develops software， there's the slow incremental approach， fixing things one by one， or the fast track， jumping feet first into Extreme Programming。 Do not be frightened by the name， it is not that extreme at all。 It is mostly good old recipes and common sense， nicely integrated together， getting rid of all the fat that has accumulated over the years。"

-- Philippe Kruchten， UBC， Vancouver， British Columbia "Sometimes revolutionaries get left behind as the movement they started takes on a life of its own。 In this book， Kent Beck shows that he remains ahead of the curve， leading XP to its next level。 Incorporating five years of feedback， this book takes a fresh look at what it takes to develop better software in less time and for less money。 There are no silver bullets here， just a set of practical principles that， when used wisely， can lead to dramatic improvements in software development productivity。"

-- Mary Poppendieck， author of Lean Software Development: An Agile Toolkit "Kent Beck has revised his classic book based on five more years of applying and teaching XP。 He shows how the path to XP is both

Download

Reviews

Hoang Dang ，

3。5/5 - This book can be written in a more succinct way。

Gary Cohen ，

I recently reread this book to refresh my understanding of XP principles。 The book is very straightforward and well-written。 While some of the sections on physical office environments may be a bit anachronistic， especially in light of the current pandemic and remote/hybrid working， the key values and principles of XP are still as relevant and important today。 This is one of the seminal software development books that should be on every developer's/manager's bookshelf。 I recently reread this book to refresh my understanding of XP principles。 The book is very straightforward and well-written。 While some of the sections on physical office environments may be a bit anachronistic， especially in light of the current pandemic and remote/hybrid working， the key values and principles of XP are still as relevant and important today。 This is one of the seminal software development books that should be on every developer's/manager's bookshelf。 。。。more

Adomas Sliužinskas ，

Five stars for the first edition， even though some of it was outdated， like remote work being impossible due to lack of communication tools at the time。

Horia ，

"The key to XP is integrity， acting in harmony with my true values"。 "Unleashing the potential of the human spirit will lead to a future for computing that we can't yet imagine。" "The key to XP is integrity， acting in harmony with my true values"。 "Unleashing the potential of the human spirit will lead to a future for computing that we can't yet imagine。" 。。。more

Jose Sanchez ，

It is still a must read if you nap doing agilityExcellent book， if you are not familiar with software you may need someone technician next door。 Sometimes it seems to offer unrealistic and inflated results but empirically you will discover the best way

Eric ，

Timeless classic。 Perhaps the best book about programming I’ve read。

Pavle ，

I really hate people forcing their view and way of working on others。 I really hate the way many authors in this field are sure in "their way" in a religious rather than professional way。 This is why this book is such a refreshment。 All ideas & methods he suggests are well argued - reader is not asked to believe him that "his method is the best"， rather he shows how & why his recommendations are sensible & useful。Another great thing that differentiates this book from others in this field， is tha I really hate people forcing their view and way of working on others。 I really hate the way many authors in this field are sure in "their way" in a religious rather than professional way。 This is why this book is such a refreshment。 All ideas & methods he suggests are well argued - reader is not asked to believe him that "his method is the best"， rather he shows how & why his recommendations are sensible & useful。Another great thing that differentiates this book from others in this field， is that it does not exist in some other dimension where everything is ideal - realities of working in a team are taken into account， and the author makes it clear that not all of his ideas are good for all， rather presenting them so that reader can choose & implement the ones he/she finds useful。Finally， probably the best mindset this book gives is the glorification of incremental improvement - nothing can be made great in day， but it can be made better。 Not all his advice is to be taken at once， but some of it can be applied， and then some more on another occasion， etc。Huge recommendation， especially for developers on beginnings of their careers。 。。。more

Joshua R。 Taylor ，

Yeah yeah， I know what you're going to say。 Trust me I've had it from everyone who's seem me reading my copy of Extreme Programming Explained。 Let me just clear this up: extreme programming is nothing like this 。。。On the contrary， the process Kent Beck describes as extreme programming sounds like one of the most relaxing， sustainable and rewarding software development frameworks I've heard of。 It is of course an ideal， but it seems realistic to be able to approach this ideal。 I feel confident in Yeah yeah， I know what you're going to say。 Trust me I've had it from everyone who's seem me reading my copy of Extreme Programming Explained。 Let me just clear this up: extreme programming is nothing like this 。。。On the contrary， the process Kent Beck describes as extreme programming sounds like one of the most relaxing， sustainable and rewarding software development frameworks I've heard of。 It is of course an ideal， but it seems realistic to be able to approach this ideal。 I feel confident in this because I have experienced most of the necessary parts in different teams I've worked in。To set the maturity bar extremely high， Beck doesn't begin with quick fixes to turn your software team around but starts with the kinds of values extreme programming is designed around。 These values sound quite inoffensive and obvious: communication， simplicity， feedback， courage， respect。 However， as any software developer or indeed anybody working in an office setting can agree， they are often forgotten or even consciously foregone。 Beck suggests that a company has to embody these values or at somebody high up in the organisation has to want them embodied， in order for extreme programming to be a good fit。Since values are very wibbly wobbly timey wimey and the bridge from values to practices can tenuous， Beck then sets out some principles to act as a bridge。 These include also very inoffensive ideals such as: improvement， quality and reflection。 However there were a few here that I found interesting。 An example was the principle of 'flow'。 Not the positive psychology kind of flow but a more abstract principle of ensuring that all software tasks should happen in one continuous motion without big discrete events。 Another example， which I am already using by name at work， is 'baby steps'。 Always take the smallest step possible to get to an outcome， in order for a high-quality whole to emerge。Lastly following on from the principles is the largest section of the book: practices。 These are far less idealistic steps to follow， probably with high appeal to the average engineer。 However I would recommend any reader to reflect harder on the values than the practices， since they really form the backbone about why you would even want to follow the practices。 Like if you don't care about communication and feedback， why would you pair programme？ If you don't care about humanity or economics， why would you plan？ So besides test-driven development and pair programming， is there anything extra that's interesting？ Firstly， Beck advocates for the time spent on design and adding value to be proportional。 This sounds incredibly controversial for most software teams， but even from a business perspective I can see the argument。 Another interesting practice is the root-cause analysis。 Beck believes that with test-driven development the rate of defects in a software system will tend towards zero。 So when a defect does occur， it doesn't just need to be fixed but also the cause of the defect needs to be fixed。 A developer is encouraged to go a layer deeper to keep the defect rate low。Overall I would recommend it to any developer who realises their job expands to more than just engineering。 It is a set of practices for delivering value through software and for feeling great as a team while making software。 Of course not every set of practices fits every context， but you should speculate anyway with regards to your own。 。。。more

Marcin ，

The book isn't revolutionary after two decades， however， it's a good sign there is hope for Software Development。 Nowadays， the majority of XP's habits are in place。 We leverage from those practices without even knowing their roots。 If you are up with IT trends （principles）， like Scrum， Agile， TDD， pair programming， you probably won't learn too much。 On the other hand， it's good to know the history and how the Agile movement started。For me， the most valuable thing was the catch the scientific ap The book isn't revolutionary after two decades， however， it's a good sign there is hope for Software Development。 Nowadays， the majority of XP's habits are in place。 We leverage from those practices without even knowing their roots。 If you are up with IT trends （principles）， like Scrum， Agile， TDD， pair programming， you probably won't learn too much。 On the other hand， it's good to know the history and how the Agile movement started。For me， the most valuable thing was the catch the scientific approach and taking a journey from values to practices through a principles bridge with the author。 。。。more

Flohallo ，

It was pretty ok。

Patrik Gustafsson ，

XP is such a good set of patterns， Raising great development practices to a system that enhancing each other。 This should be read by anyone taking part in a development team or tightly interacting with it。

Matthew ，

A great introduction to the fundamental values， principles， and practices of Extreme Programming

Paolo ，

Great book that highlights some of the struggles of the traditional software development and how to overcome its main problems。My sensation is that the author explains very well the principles and values， but the practices explanation is a bit short， although， as the author remarks， they’re not the most important part of XP。

Ismail Mayat ，

Some really profound insights into software development， it's an old book maybe some of the practices are no more mainstream， however still recommend it as must read for every developer。Will be on my desk as a reference。 Some really profound insights into software development， it's an old book maybe some of the practices are no more mainstream， however still recommend it as must read for every developer。Will be on my desk as a reference。 。。。more

Mario Galaviz ，

Buenas técnicas。 Aunque no tengo conocimiento de programación， ahora puedo entender un poco más las mejores prácticas de desarrollo

Jimmy Cerone ，

A fascinating framework for getting anything done。 Don't take the title to seriously， this is extreme， but not in the ways you might assume。 A fascinating framework for getting anything done。 Don't take the title to seriously， this is extreme， but not in the ways you might assume。 。。。more

Muhammad Fareed ，

It just amazes me， that this book from 2005 and yet in 2020 is still relevant and have many answers to a lot of problems we face with every day software engineering。 It just makes me sad to see that yet another method of efficient software engineering has been overlooked or bot used in a lot of organizations， and what I mean is that many organizations just uses the name and bot really get the essence of that method。

Tianyao Chen ，

Not very applicable。 The Wikipedia page provides a more organized summary of XP。

Norent Khy ，

The way I see it， the contents of this book speak to your beliefs。 This can make people strongly like or dislike its contents。 I was surprised to see Nonviolent Communication in the annotated bibliography。 And now in retrospect， it only makes sense。The comparison with the TPS， made a lot of sense。 Kent's reminders that we're all humans in various ways， made it a pleasure to read。 The way I see it， the contents of this book speak to your beliefs。 This can make people strongly like or dislike its contents。 I was surprised to see Nonviolent Communication in the annotated bibliography。 And now in retrospect， it only makes sense。The comparison with the TPS， made a lot of sense。 Kent's reminders that we're all humans in various ways， made it a pleasure to read。 。。。more

Dardan Bekteshi ，

Kent is a brilliant writer。 Such an enjoyable read。 A must for any software practitioner。

Bart ，

A great book for learning about software and humans。

Dmitry Berezhnoy ，

This book is tiny enough to finish in one go （though I did read it slowly one paragraph at a time）。It offers a framework of values， principles， and practices， that enables more efficient software development and better communication。At the same time， the author does not dictate which tools must be used or how much time should be dedicated to certain activities。Instead， the book offers a number of stories that provide a better idea of when and how the framework can be applied。Personally， I was fa This book is tiny enough to finish in one go （though I did read it slowly one paragraph at a time）。It offers a framework of values， principles， and practices， that enables more efficient software development and better communication。At the same time， the author does not dictate which tools must be used or how much time should be dedicated to certain activities。Instead， the book offers a number of stories that provide a better idea of when and how the framework can be applied。Personally， I was familiar with many （if not most） of the principles and practices。What stood out to me was the overarching idea of integrity between the key three components （values， principles， and practices）。 。。。more

Abhishek Sah ，

This book introduces the essence behind XP。 It will tell you how XP improves software delivery by following some battle-tested best practices。 This book attempts to develop a customer-centric software delivery model in the minds of the readers。 A good read！

Harish Babu ，

Short and to the pointI have put off reading about XP for a while because I thought that it wasn’t required to be a good developer。 I stand corrected now and would recommend this book to be a requirement for all developers。

David Dikman ，

Pragmatic approach to XPHonestly， I had thought to read this for a long， long time。 Always striving towards the ideal I thought XP was but now I think I see it more as a personal journey than a clear goal。 Which is fine of course， but I think I was hoping for more clear directive of how you can practically apply it。But as with any other working styles， I guess it depends incredibly much on the context， the goal， business and team。It was still an enlightening read。

Anton ，

Неплохая реклама экстремального программированияВсе как обычно встает в вопрос ожиданий。 От книги с названием Extreme Programming Explained я ожидал довольно досконального объяснения техник экстремального программирования， описания как и почему они работают。 Вместо этого я получил кучу информации формата "пишите сначала тесты потому что вы таким образом дизайните решение" или "занимайтесь парным программированием потому что это классно"。 Из интересного я здесь подчерпнул следующее:- Если у вас н Неплохая реклама экстремального программированияВсе как обычно встает в вопрос ожиданий。 От книги с названием Extreme Programming Explained я ожидал довольно досконального объяснения техник экстремального программирования， описания как и почему они работают。 Вместо этого я получил кучу информации формата "пишите сначала тесты потому что вы таким образом дизайните решение" или "занимайтесь парным программированием потому что это классно"。 Из интересного я здесь подчерпнул следующее:- Если у вас назревает срач или большой аргумент можно залимитировать митинг 15 минутами и начать делать ХОТЬ ЧТО ТО。 Это на самом деле не новость， я так с программированием делаю: когда не знаешь как назвать переменную назови ее как угодно， потом разберешься。 В народе это известно как fail fast。- Докапывания до источника косяка。 Когда есть багуля， сначала мы пишем интеграционный тест который ее воспроизводит。 Потом мы пишем юнит тест。 Потом чиним багулю。 Потом смотрим что прошел юнит тест， потом что интеграционный。 Дальше мы начинаем последовательно спрашивать откуда эта багуля возникла， в формате "не подумал？ а почему не подумал"- TDD можно применять не только с юнит тестами。 Можно начать делать фичу с написания Е2Е теста который будет заодно и спекой задачи служить。 Мне сложно это представить в реальном мире （хотя бы потому что Е2Е нерабочее говно）， но идея интересная。Книгу можно посоветовать если вы никогда не слышали про экстремальное программирование， TDD， Pair Programming и вот это все。 Мне сложно представить что такие есть в 2020 году， впрочем。 。。。more

Marcin Golenia ，

I read it 15 years after release， so 15 years too late。 After so much time the book is not so innovative but 15 years ago and 20 years ago （first edition） it was visionary。 I could not give it less because I was late :） The book is easy to read， highly inspiring and well organised。 It leads you from values through practices and principles to roles and more insightful chapters like Designing: The Value of Time - which was and still is so much needed in our industry。 The mention about TPS stole my I read it 15 years after release， so 15 years too late。 After so much time the book is not so innovative but 15 years ago and 20 years ago （first edition） it was visionary。 I could not give it less because I was late :） The book is easy to read， highly inspiring and well organised。 It leads you from values through practices and principles to roles and more insightful chapters like Designing: The Value of Time - which was and still is so much needed in our industry。 The mention about TPS stole my heart - it is short but yet valuable and inspiring do keep digging into lean。 Agile has lost its way - we should go back to the roots。 XP is one of the root。 Strongly recommend read even in 2020。 。。。more

Olivier Grange-Labat ，

The classic book by computer legend Kent Beck， documenting XP， a set of values， principles and practices for delivering software。Filed in “must-read for every developer and tech manager”， part because it is full of wisdom and excellent advices， part because it helps reflect on our own practices and define our own style。Being a short book makes it even better and annotated bibliography is a great addition。

Gonzalo Gómez Sullain ，

If you were already in contact with agile frameworks， it might not add new things， although will put all the ideas， concepts and values aligned。 It will sort the core ideas behind titles。For everyone trying to make a shift in his/her software development approach mindset， is a a mandatory book。 This book is the root， and since it is the second edition， it also explains how the seed idea came up and evolved since the initial iteration。 For me it consolidated the concepts spread around， and allowe If you were already in contact with agile frameworks， it might not add new things， although will put all the ideas， concepts and values aligned。 It will sort the core ideas behind titles。For everyone trying to make a shift in his/her software development approach mindset， is a a mandatory book。 This book is the root， and since it is the second edition， it also explains how the seed idea came up and evolved since the initial iteration。 For me it consolidated the concepts spread around， and allowed me to consolidate the core ideas behind titles with a reasoning behind。 。。。more

Herve Tunga ，

Very good overview of the practice。

Reference

google book https://www.google.com/search?tbm=bks&q=Extreme Programming Explained: Embrace Change (The XP Series)

hathitrust digital library https://babel.hathitrust.org/cgi/ls?q1=Extreme Programming Explained: Embrace Change (The XP Series)&field1=ocr&a=srchls&ft=ft&lmt=ft

The British Library https://bll01.primo.exlibrisgroup.com/discovery/search?query=any,contains,Extreme Programming Explained: Embrace Change (The XP Series)&tab=LibraryCatalog&search_scope=Not_BL_Suppress&vid=44BL_INST:BLL01&lang=en&offset=0